New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The word landmark is no longer abbreviated in braille #13158
Milestone
Comments
It looks like |
Merged
5 tasks
feerrenrut
pushed a commit
that referenced
this issue
Dec 14, 2021
…lle (PR #13160) Fixes #13158 PR #12814 replaced usages of deprecated controlTypes.roleLabels with role.displayString. However braille has its own mapping of roles to labels which should be used for abbreviations of roles for braille. The role label used for speech has been mistakenly used for a role of landmark.
Please test and confirm this is fixed in the RC for 2021.3.1: https://www.nvaccess.org/post/nvda-2021-3-1rc1/ |
Confirmed as fixed. |
I can confirm that this issue is fixed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Steps to reproduce:
Actual behavior:
The braille display shows:
"landmark navi h1 lnk gra NV Access"
Expected behavior:
The display shows:
"lmk navi h1 lnk gra NV Access"
That is, "landmark" should be "lmk", just as "navigation" is shortened to "navi".
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
2021.3
Windows version:
Windows 10 21H2 (10.0.19044) workstation
Name and version of other software in use when reproducing the issue:
Firefox 95.0
Other information about your system:
N/A
Other questions
Does the issue still occur after restarting your computer?
Yes
Have you tried any other versions of NVDA? If so, please report their behaviors.
Yes, "lmk" is shown in 2021.2 and the release notes does not mention this change.
If NVDA add-ons are disabled, is your problem still occurring?
Yes
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
Yes
The text was updated successfully, but these errors were encountered: